bouncycastle legion-of-the-bouncy-castle-java-crytography-api vulnerabilities and exploits

(subscribe to this query)

NA

The TLS implementation in the Bouncy Castle Java library prior to 1.48 and C# library prior to 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote malicious users to c...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.12 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.11 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.20 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.17 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.04 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.03 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.08 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.07 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.06 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.16 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.13 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.23 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.24 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.32 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.31 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.43 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.44 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.02 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.01 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.05 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.19 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.14

NA

The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package prior to 1.36, has unknown impact and remote attack vectors related to "a Bleichenbacher vulnerability in simple RSA CMS signatures without signed attributes."

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.31 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.30 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.29 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.22 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.21 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.14 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.13 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.05 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.04 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.33 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.32 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.23 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.24 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.16 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.15 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.08 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.07 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.06 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.36 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.28 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.27 Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.20

7.4

CVSSv3

In the Bouncy Castle JCE Provider version 1.55 and previous versions the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api

5.9

CVSSv3

BouncyCastle TLS prior to version 1.0.3, when configured to use the JCE (Java Cryptography Extension) for cryptographic functions, provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a ...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api

7.5

CVSSv3

In Bouncy Castle JCE Provider version 1.55 and previous versions the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow ...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api

7.4

CVSSv3

In the Bouncy Castle JCE Provider version 1.55 and previous versions the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api

5.9

CVSSv3

In the Bouncy Castle JCE Provider version 1.55 and previous versions the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryptio...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api Debian Debian Linux 8.0

3.7

CVSSv3

In the Bouncy Castle JCE Provider version 1.55 and previous versions the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of rel...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api Debian Debian Linux 8.0

4.4

CVSSv3

The default BKS keystore use an HMAC that is only 16 bits long, which can allow an malicious user to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore gener...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api Redhat Satellite 6.4 Redhat Satellite Capsule 6.4

5.5

CVSSv3

The AES-GCM specification in RFC 5084, as used in Android 5.x and 6.x, recommends 12 octets for the aes-ICVlen parameter field, which might make it easier for malicious users to defeat a cryptographic protection mechanism and discover an authentication key via a crafted applicati...

Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.54 Google Android 5.1.0 Google Android 6.0.1 Google Android 6.0 Google Android 5.0.1 Google Android 5.0 Google Android 5.1

Get Started

1 2 NEXT »

Vulmon Search is a vulnerability search engine. It gives comprehensive vulnerability information through a very simple user interface.

Home Recent Vulnerabilities Research Posts Trends Blog About Contact

Vulmon Search Vulmon Research Vulmon Alerts Vulmap

Twitter Reddit Linkedin Facebook